chore: Update k8s version to 1.30 #3748
Conversation
nikoshet
force-pushed
the
chore/bump-k8s-version-to-1.30
branch
7 times, most recently
from
6ee7b62
to
a548264
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3748 +/- ##
==========================================
- Coverage 83.96% 83.95% -0.02%
==========================================
Files 162 162
Lines 18508 18508
==========================================
- Hits 15540 15538 -2
- Misses 2106 2107 +1
- Partials 862 863 +1 ☔ View full report in Codecov by Sentry. |
Published E2E Test Results 4 files 4 suites 3h 18m 54s ⏱️ For more details on these failures, see this check. Results for commit 870c629. ♻️ This comment has been updated with latest results. |
Published Unit Test Results2 257 tests 2 257 ✅ 2m 59s ⏱️ Results for commit 870c629. ♻️ This comment has been updated with latest results. |
zachaller
force-pushed
the
chore/bump-k8s-version-to-1.30
branch
from
a548264
to
217c733
Compare
|
We should remove on on the tail end like 1.26. |
Signed-off-by: nikoshet <[email protected]>
Signed-off-by: Zach Aller <[email protected]>
zachaller
force-pushed
the
chore/bump-k8s-version-to-1.30
branch
from
5f7f06e
to
870c629
Compare
|
|
Any plan in near future to support K8S v1.30. We want to upgrade the k8s and we are blocked. |
|
@mansing2 I would not let what clients Rollouts uses cause you to not upgrade your k8s cluster. As long as you do not use any of the new pod spec fields if there are any it will be ok we use very little k8s feature set. The only big one being the embedded pod spec into the rollout resource. |
Checklist:
"fix(controller): Updates such and such. Fixes #1234".